System, method, and computer-readable medium for indirect routing of mobile-originated SMS messages for a mobile station attached with an IP-femtocell system

ABSTRACT

A system, method, and computer readable medium that facilitate indirect routing of mobile-originated short messages for a mobile station attached with a femtocell system are provided. A convergence server uses indirect routing for delivery of a short message. The MS may elect to use a traffic or paging channel for delivery of the short message. If the MS selects the traffic channel for delivery of the message and if there is no existing traffic channel, the MS may first attempt to establish a traffic channel. If an active traffic channel is already established between the mobile station and the femtocell system, the mobile station sends the message to the femtocell system which, in turn, forwards the message to the convergence server. If the MS elects to send the message over a paging channel, the MS sends the message along with authentication data to the femtocell system that first performs authentication and subsequently forwards the message to the convergence server which, in turn, forwards the short message to the home message center.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. Ser. No. 12/605,526,filed on Oct. 26, 2009, entitled “SYSTEM, METHOD, AND COMPUTER-READABLEMEDIUM FOR INDIRECT ROUTING OF MOBILE-ORIGINATED SMS MESSAGES FOR AMOBILE STATION ATTACHED WITH AN IP-FEMTOCELL SYSTEM”, now issued U.S.Pat. No. 9,661,481, issued on May 23, 2017, which is acontinuation-in-part of U.S. Ser. No. 12/252,231 filed Oct. 15, 2008,entitled, “SYSTEM, METHOD, AND COMPUTER-READABLE MEDIUM FOR PROCESSINGCALL ORIGINATIONS BY A FEMTOCELL SYSTEM”, now issued U.S. Pat. No.8,194,590, issued on Jun. 05, 2012, which is a continuation-in-part ofU.S. Ser. No. 12/252,238 filed Oct. 15, 2008, entitled, “SYSTEM, METHOD,AND COMPUTER-READABLE MEDIUM FOR SHORT MESSAGE SERVICE PROCESSING BY AFEMTOCELL SYSTEM”, now issued U.S. Pat. No. 8,792,920, issued on Jul.29, 2014, which is a continuation-in-part of U.S. Ser. No. 12/252,246filed on Oct. 15, 2008, entitled, “SYSTEM, METHOD, AND COMPUTER-READABLEMEDIUM FOR USER EQUIPMENT REGISTRATION AND AUTHENTICATION PROCESSING BYA FEMTOCELL SYSTEM”, now issued U.S. Pat. No. 8,351,901, issued on Jan.08, 2013, the disclosures of each of which are incorporated herein byreference and each of which claim priority to U.S. provisional patentapplication Ser. No. 61/003,151, entitled, “SIP-IOS adapter function”,filed Nov. 15, 2007, the disclosure of which is incorporated herein byreference. Incorporated by reference is commonly assigned: U.S. Ser. No.12/252,237 filed Oct. 15, 2008, entitled, “SYSTEM, METHOD, ANDCOMPUTER-READABLE MEDIUM FOR CALL TERMINATION PROCESSING BY A FEMTOCELLSYSTEM” and U.S. Ser. No. 12/252,242 filed Oct. 15, 2008, entitled,“SYSTEM, METHOD, AND COMPUTER-READABLE MEDIUM FOR SHORT MESSAGE SERVICETERMINATION PROCESSING BY A FEMTOCELL SYSTEM” and U.S. Ser. No.12/252,199 filed Oct. 15, 2008, entitled, “SYSTEM, METHOD, ANDCOMPUTER-READABLE MEDIUM FOR IP-FEMTOCELL PROVISIONED RADIO ACCESSNETWORK” and U.S. Ser. No. 12/252,202 filed Oct. 15, 2008, entitled,“SYSTEM, METHOD, AND COMPUTER-READABLE MEDIUM FOR USER EQUIPMENT HANDOFFWITHIN AN IP-FEMTOCELL NETWORK” and U.S. Ser. No. 12/252,204 filed Oct.15, 2008, entitled, “SYSTEM, METHOD, AND COMPUTER-READABLE MEDIUM FORUSER EQUIPMENT ACQUISITION OF AN IP-FEMTOCELL SYSTEM” and U.S. Ser. No.12/252,210 filed Oct. 15, 2008, entitled, “SYSTEM, METHOD, ANDCOMPUTER-READABLE MEDIUM FOR USER EQUIPMENT HANDOFF FROM A MACROCELLULARNETWORK TO AN IP-FEMTOCELL NETWORK” and U.S. Ser. No. 12/252,212 filedOct. 15, 2008, entitled, “SYSTEM, METHOD, AND COMPUTER-READABLE MEDIUMFOR CONFIGURATION OF AN IP-FEMTOCELL SYSTEM” and U.S. Ser. No.12/252,217 filed Oct. 15, 2008, entitled, “SYSTEM, METHOD, ANDCOMPUTER-READABLE READABLE MEDIUM FOR MOBILE-TO-MOBILE CALLS WITHINFEMTOCELL NETWORK” and U.S. Ser. No. 12/252,222 filed Oct. 15, 2008,entitled, “SYSTEM, METHOD, AND COMPUTER-READABLE MEDIUM FOR ACCESSRESTRICTION OF USER EQUIPMENT DEVICES IN AN IP-FEMTOCELL SYSTEM” andU.S. Ser. No. 12/252,226 filed Oct. 15, 2008, entitled, “SYSTEM, METHOD,AND COMPUTER-READABLE MEDIUM FOR ABBREVIATED-CODE DIALING IN A NETWORKSYSTEM” and U.S. Ser. No. 12/252,227 filed Oct. 15, 2008, entitled,“SYSTEM, METHOD, AND COMPUTER-READABLE MEDIUM FOR MULTI-STAGE TRANSMITPROTECTION IN A FEMTOCELL SYSTEM” and U.S. Ser. No. 12/252,234 filedOct. 15, 2008, entitled, “SYSTEM, METHOD, AND COMPUTER-READABLE MEDIUMFOR MOBILE TERMINATED CALL PROCESSING BY A FEMTOCELL SYSTEM” and PCTSer. No. PCT/US08/80031 filed Oct. 15, 2008, entitled, “SYSTEM, METHOD,AND COMPUTER-READABLE MEDIUM FOR PROCESSING CALL ORIGINATIONS BY AFEMTOCELL SYSTEM” and PCT Ser. No. PCT/US08/80032 filed Oct. 15, 2008,entitled, “SYSTEM, METHOD, AND COMPUTER-READABLE MEDIUM FOR SHORTMESSAGE SERVICE PROCESSING BY A FEMTOCELL SYSTEM” and PCT Ser. No.PCT/US08/80033 filed Oct. 15, 2008, entitled, “SYSTEM, METHOD, ANDCOMPUTER-READABLE MEDIUM FOR USER EQUIPMENT REGISTRATION ANDAUTHENTICATION PROCESSING BY A FEMTOCELL SYSTEM”.

FIELD OF THE INVENTION

The present invention is generally related to radio access technologiesand, more particularly, to mechanisms for facilitating mobile stationregistration and authentication via a femtocell system.

BACKGROUND OF THE INVENTION

Contemporary cellular radio systems, or mobile telecommunicationsystems, provide an over-the-air interface to wireless mobile stations(MSs), also referred to as user equipments (UEs), via a radio accessnetwork (RAN) that interfaces with at least one core network. The RANmay be implemented as, for example, a CDMA2000 RAN, a Universal MobileTelecommunications System (UMTS) RAN, a Global System for Mobilecommunications (GSM) RAN, or another suitable radio access networkimplementation. The MSs may comprise, for example, a mobile terminalsuch as a mobile telephone, a laptop computer featuring mobile telephonysoftware and hardware, a personal digital assistant (PDA), or othersuitable equipment adapted to transfer and receive voice or datacommunications with the radio access network.

A RAN covers a geographical area comprised of any number of cells eachcomprising a relatively small geographic area of radio coverage. Eachcell is provisioned by a cell site that includes a radio tower, e.g., abase transceiver station (BTS), and associated equipment. BTSscommunicate with MSs over an air interface within radio range of theBTSs.

Numerous BTSs in the RAN may be communicatively coupled to a basestation controller (BSC), also commonly referred to as a radio networkcontroller (RNC). The BSC manages and monitors various system activitiesof the BTSs serviced thereby. BSCs are typically coupled with at leastone core network.

BTSs are typically deployed by a carrier network in areas having a highpopulation density. The traffic capacity of a cell site is limited bythe site's capacity and affects the spacing of cell sites. In suburbanareas, sites are often up to two miles apart, while cell sites deployedin dense urban areas may be as close as one-quarter of a mile apart.Because the traffic capacity of a cell site is finitely limited, as isthe available frequency spectrum, mobile operators have a vestedinterest in technologies that allow for increased subscriber capacity.

A microcell site comprises a cell in a mobile phone network that coversa limited geographic area, such as a shopping center, hotel, airport, orother infrastructure that may have a high density mobile phone usage. Amicrocell typically uses power control to limit the radius of themicrocell coverage. Typically a microcell is less than a mile wide.

Although microcells are effective for adding network capacity in areaswith high mobile telephone usage, microcells extensively rely on theRAN, e.g., a controlling BSC and other carrier functions. Becausecontemporary BSCs have limited processing and interface capacity, thenumber of BTSs - whether microcell BTSs or typical carrier BTSs - ableto be supported by the BSC or other RAN functions is disadvantageouslylimited.

Contemporary interest exists in providing enterprise and office access,including small office/home office (SOHO) radio access, by an evensmaller scale BTS. The radio coverage area of such a system is typicallyreferred to as a femtocell. In a system featuring a femtocell, an MS maybe authorized to operate in the femtocell when proximate the femtocellsystem, e.g., while the MS is located in the SOHO. When the MS movesbeyond the coverage area of the femtocell, the MS may then be servicedby the carrier network. The advantages of deployment of femtocells arenumerous. For instance, mobile users frequently spend large amounts oftime located at, for example, home, and many such users rely extensivelyon cellular network service for telecommunication services during thesetimes. For example, a recent survey indicated that nearly thirteenpercent of U.S. cell phone customers do not have a landline telephoneand rely solely on cell phones for receiving telephone service. From acarrier perspective, it would be advantageous to have telephone servicesprovisioned over a femtocell system, e.g., deployed in the user's home,to thereby reduce the load and effectively increase the capacity on thecarrier RAN infrastructure. However, no mechanisms have been providedfor efficiently providing a convergence of femtocell and macrocellularsystems in a manner that facilitates delivery of mobile-originated shortmessage service (SMS) messages of a mobile station attached with afemtocell system.

Therefore, what is needed is a mechanism that overcomes the describedproblems and limitations.

SUMMARY OF THE INVENTION

In accordance with disclosed embodiments, mechanisms that facilitateindirect routing of mobile-originated short message service (SMS)messages for a mobile station attached with a femtocell system areprovided. A convergence server (CS) operating as the Visitor LocationRegister/Mobile Switching Center uses indirect routing, e.g., byforwarding a mobile-originated short message to the home message center(MC) of the mobile station. Thereafter, the short message is sent to thedestination MC. Depending on the existence of an assigned trafficchannel for the MS and/or the size of the SMS message being sent, the MSmay elect to use a traffic or paging channel for delivery of the shortmessage. If the MS selects the traffic channel for delivery of the SMSmessage and if there is no existing traffic channel, the MS may firstattempt to establish a traffic channel. If an active traffic channel isalready established between the MS and the femtocell system, the MSsends the SMS message to the femtocell system which, in turn, forwardsthe SMS message to the CS. If the MS elects to send the SMS message overa paging channel, the MS sends the SMS message along with 1xauthentication data to the femtocell system. The femtocell system firstperforms the authentication, and subsequently forwards the SMS messageto the CS which, in turn, forwards the short message to the home messagecenter of the MS that originated the SMS message.

In accordance with an embodiment, a method of facilitating indirectrouting of mobile-originated short messages for a mobile stationattached with a femtocell system is provided. The method includesreceiving, by a convergence server deployed in a core network, a servicerequest message for a mobile station attached with a femtocell system,engaging, by the convergence server, a mobile core network in anauthentication process for the mobile station, responsive to theauthentication process, transmitting, by the convergence server, aglobal challenge response to the femtocell system, receiving, by theconvergence server, a short message originated by the mobile stationfrom the femtocell system, and transmitting, by the convergence server,the short message to a home message center of the mobile station.

In accordance with another embodiment, a computer-readable medium havingcomputer-executable instructions tangibly embodied thereon for executionby a processing system, the computer-executable instructions forfacilitating indirect routing of mobile-originated short messages for amobile station attached with a femtocell system, is provided. Thecomputer-readable medium includes instructions that, when executed,cause the processing system to receive, by a convergence server deployedin a core network, a service request message for a mobile stationattached with a femtocell system, engage, by the convergence server, amobile core network in an authentication process for the mobile station,transmit, by the convergence server, a global challenge response messageincluding an authentication token to the femtocell system, responsive tothe authentication process, transmit, by the convergence server, aglobal challenge response to the femtocell system, receive, by theconvergence server, a short message originated by the mobile stationfrom the femtocell system, and transmit, by the convergence server, theshort message to a home message center of the mobile station.

In accordance with another embodiment, a network system that facilitatesindirect routing of mobile-originated short messages for a mobilestation attached with a femtocell system is provided. The systemincludes a core network that includes a convergence server, a mobilecore network that includes an authentication center, a Home LocationRegister, and a message center, and an Internet Protocol-based femtocellsystem that provides a radio access point for a mobile station. Theconvergence server receives a service request message for the mobilestation, engages the mobile core network in an authentication processfor the mobile station, transmits a global challenge response messageincluding an authentication token to the femtocell system, responsive tothe authentication process, transmits a global challenge response to thefemtocell system, receives a short message originated by the mobilestation from the femtocell system, and transmits the short message tothe message center.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the present disclosure are best understood from the followingdetailed description when read with the accompanying figures, in which:

FIG. 1 is a diagrammatic representation of a network system thatincludes a cellular network adapted to provide macro-cellular coverageto a mobile station;

FIG. 2 is a diagrammatic representation of a conventional network systemconfiguration featuring a femtocell system;

FIG. 3A is a diagrammatic representation of a network system in which afemtocell system implemented in accordance with an embodiment of theinvention may be deployed;

FIG. 3B is a diagrammatic representation of an alternative networksystem in which a femtocell system implemented in accordance with anembodiment of the invention may be deployed;

FIG. 4 is a simplified diagrammatic representation of femtocell systemthat facilitates provisioning of a femto-RAN in accordance with anembodiment;

FIG. 5 depicts a block diagram of a data processing system that may beimplemented as a convergence server in accordance with an embodiment ofthe present invention;

FIG. 6 depicts a diagrammatic representation of a registration andauthentication process on initial system access by a mobile station viaa femtocell system in a non-Internet Protocol Multimedia Subsystemnetwork implemented in accordance with an embodiment;

FIG. 7 depicts a diagrammatic representation of a registration andauthentication process on initial system access by a mobile station viaa femtocell system in an Internet Protocol Multimedia Subsystem networkimplemented in accordance with an embodiment;

FIG. 8 depicts a diagrammatic representation of a signaling flow of amobile-originated short message service delivery procedure utilizingindirect routing in accordance with an embodiment;

FIG. 9A is a diagrammatic representation of a service request messagetransmitted to the convergence server from a femtocell systemimplemented in accordance with an embodiment; and

FIG. 9B is a diagrammatic representation of a global challenge responsemessage transmitted to the femtocell system from the convergence serverin accordance with an embodiment.

DETAILED DESCRIPTION OF THE INVENTION

It is to be understood that the following disclosure provides manydifferent embodiments or examples for implementing different features ofvarious embodiments. Specific examples of components and arrangementsare described below to simplify the present disclosure. These are, ofcourse, merely examples and are not intended to be limiting.

FIG. 1 is a diagrammatic representation of a network system 100 thatincludes a cellular network 110 adapted to provide macro-cellularcoverage to a mobile station. Cellular network 110 may comprise, forexample, a code-division multiple access (CDMA) network, such as aCDMA-2000 network.

Cellular network 110 may include any number of base transceiver stations(BTSs) 112 a-112 c communicatively coupled with a base stationcontroller (BSC) 114 or RNC. Each individual BTS 112 a-112 c under thecontrol of a given BSC may define a radio cell operating on a set ofradio channels thereby providing service to an MS 125, such as a mobileterminal. BSC 114 manages the allocation of radio channels, receivesmeasurements from mobile terminals, controls handovers, as well asvarious other functions as is understood. BSC 114 is interconnected witha Mobile Switching Center (MSC) 116 that provides mobile terminalexchange services. BSC 114 may be additionally coupled with a packetdata serving node (PDSN) 118 or other gateway service that provides aconnection point between the CDMA radio access network and a packetnetwork, such as Internet 160, and provides mobility managementfunctions and packet routing services. MSC 116 may communicativelyinterface with a circuit switched network, such as the public switchedtelephone network (PSTN) 150, and may additionally be communicativelycoupled with an interworking function (IWF) 122 that provides aninterface between cellular network 110 and PSTN 150.

System 100 may also include a signaling system, such as a signalingsystem #7 (SS7) network 170. SS7 network 170 provides a set of telephonysignaling protocols which are used to set up the vast majority of theworld's PSTN telephone calls. SS7 network 170 is also used in cellularnetworks for circuit switched voice and packet-switched dataapplications. As is understood, SS7 network 170 includes varioussignaling nodes, such as any number of service control points (SCPs)172, signal transfer points (STPs) 174, and service switching points(SSPs) 176.

BTSs 112 a-112 c deployed in cellular network 110 may service numerousnetwork 110 subscribers. Cell cites provided by BTSs 112 a-112 ccommonly feature site ranges of a quarter to a half mile, e.g., indensely populated urban areas, to one to two miles in suburban areas. Inother remotely populated regions with suitable geography, site rangesmay span tens of miles and may be effectively limited in size by thelimited transmission distance of relatively low-powered MSs. As referredto herein, a cell provided by a BTS deployed in carrier network 110 foraccess by any authorized network 110 subscriber is referred to as amacrocell.

FIG. 2 is a diagrammatic representation of a conventional network system200 configuration featuring a femtocell. In the depicted example, acentral BSC 214 deployed in a cellular carrier network 210 may connectwith a soft switch core 212 that is connected with a MSC 216. MSC 216connects with the cellular core network and may interface with othernetworks, such as the PSTN as is understood. BSC 214 may be connectedwith and service numerous BTSs 212 a-212 c that provide macrocells tocellular network 210 subscribers.

BSC 214 may additionally connect with a tunnel gateway system 218 thatis adapted to establish secured tunnels 232 a-232 x with respectivefemtocell systems 250 a-250 x. Femtocells comprise cellular accesspoints that connect to a mobile operator's network using, for example, aresidential Digital Subscriber Line (DSL) or cable broadband connection.Femtocells 250 a-250 x provide a radio access point for MS 225 when theMS is within range of a femtocell system with which the MS hasauthorized access. For example, femtocell system 250 a may be deployedin a residence of the user of MS 225. Accordingly, when the user iswithin the residence, mobile telecommunications may be provided to MS225 via an air-interface provided by femtocell system 250 a. In thisinstance, MS 225 is effectively offloaded from the macro BTS, e.g., BTS212 a, and communications to and from the MS are carried out withfemtocell system 250 a over Internet 260. Thus, femtocell systems 250a-250 x may reduce the carrier radio resource demands by offloading MSsfrom macrocells to femtocells and thereby provide for increasedsubscriber capacity of cellular network 210.

In contemporary implementations such as that depicted in FIG. 2, afemtocell system 250 a comprises a transceiver without intelligence andis thus required to be connected and managed by BSC 214. Thus, femtocellsystems 250 a-250 x are reliant on the carrier network centralized BSC214 which has limited capacity and thus does not exhibit desirablescaling characteristics or capabilities. Moreover, high communicationsoverhead are realized by the BTS backhaul.

FIG. 3A is a diagrammatic representation of a network system 300 inwhich a femtocell system implemented in accordance with an embodiment ofthe invention may be deployed. System 300 includes a mobile core network310 implemented as, for example, a code division multiple access (CDMA)core network that interfaces with a SS7 network 370. Mobile core network310 may include a Messaging Center (MC) 312, a Home Location Register(HLR) 314, an authentication center (AC) 315, a Mobile Switching Center(MSC) 316, a Packet Data Serving Node (PDSN) 318, and various othercomponents. The HLR 314 is a central database that contains details ofeach MS subscriber authorized to use the mobile core network 310. Theremay be several HLRs deployed in the core network 310. The HLR 314maintains details of each Subscriber Identity Module (SIM) card issuedby the mobile network operator, e.g., the International MobileSubscriber Identity (IMSI) stored in the SIM card, services authorizedfor the associated user, a location of the MS, and various otherinformation. The HLR 314 may interface with the AC 315 that functions tofacilitate authentication of MSs that access the cellular network. TheMSC 316 provides mobile terminal exchange services and maycommunicatively interface with a circuit switched network, such as thepublic switched telephone network. The MSC 316 handles voice calls andShort Message Service (SMS), sets up and releases end-to-endconnections, and handles mobility and hand-over requirements duringcalls as well as other functions. The PDSN 318 provides an interfacebetween the radio access and IP networks. The PDSN 318 provides, forexample, mobility management functions and packet routing functionality.

System 300 includes an Internet Protocol (IP) core network 320 thatinterfaces with the SS7 network 370, e.g., via IS-41. In accordance withan embodiment, the IP core network 320 includes a convergence server(CS) 322, a softswitch/Media Gateway Controller Function (MGCF) 324, anda Media Gateway (MGW) 326 among other components. The CS 322 may becommunicatively coupled with the SS7 network 370 and a Packet DataInterworking Function (PDIF) 332, e.g., via Session Initiation Protocol(SIP) communications. The CS 322 provides SIP registration functions anda central interface point to Voice over Internet Protocol (VoIP)elements and the softswitch/MGCF 324. The CS 322 further providesSIP-MSC and Interworking functions between existing VoIP networkelements and the operator's core network. To this end, the CS 322 mayinterface directly with the MC 312 and the HLR 314 using, for example, aTIA-41 interface.

The softswitch/MGCF 324 may be communicatively coupled with the CS 322,e.g., via SIP communications, with the SS7 network 370, and with the MGW326. The softswitch/MGCF 324 may connect calls from one device toanother and perform call control protocol conversion, for example,between SIP and ISDN User Part (ISUP). The MGW 326 may becommunicatively coupled with the SS7 network 370 and the PDIF 332 inaddition to the softswitch/MGCF 324. The MGW 326 may convert databetween real-time transport protocol (RTP) and pulse code modulation(PCM), and may also be employed for transcoding. Resources of the MGW326 may be controlled by the softswitch/MGCF 324.

In accordance with an embodiment, the system 300 may include a SecurityServer (SS) 330 that interfaces with the SS7 network 370, e.g., viaIS-41, and the PDIF 332, e.g., via a Wm interface. The PDIF 332facilitates access to the IP core network 320 via WiFi access points andmay be responsible for such services as, for example, security, access,authentication, policy enforcement, user information collection, and IPaddress allocation as well as other services. The PDIF 332 mayinterface, e.g., via SIP communications, with the CS 322, and may haveReal-time Transport Protocol (RTP) communications with the MGW 326.Further, the PDIF 332 may have secured IP communications, e.g., IPsec,established with one or more femtocell systems, e.g., a femtocell system350 deployed at a user premise, such as a home office. The securedcommunications may be established between the PDIF 332 and the femtocellsystem 350 over, for example, a broadband network 360 interface such asa residential DSL or cable broadband connection. The femtocell system350, in turn, provides a radio access point for one or more MSs 325 whenthe MS 325 is within range of the femtocell system 350 with which the MS325 has authorized access.

In accordance with an embodiment, a femtocell system 350 may includeintegrated BTS and BSC functions and may feature additional capabilitiesavailable in the provided femtocell site coverage area. Femtocell system350 provides an IP-accessible radio access network, is adapted foroperation with IP core network 320, and provides radio link controlfunctions. Femtocell system 350 may be communicatively coupled withbroadband network 360 via any variety of backhaul technologies, such asan 802.11x link, a 10/100 BaseT LAN link, a T1/E1 Span or fiber, cableset top box, DSL modem connected with a central office digitalsubscriber line access multiplexer, a very small aperture terminal(VSAT), or another suitable backhaul infrastructure.

In an embodiment, femtocell system 350 includes a session initiationprotocol (SIP) adapter that supports a SIP client pool and providesconversion of call set-up functions to SIP client set-up functions. Tothis end, the femtocell system 350 may be allocated an IP address.Additionally, femtocell system 350 includes electronic serial number(ESN) screening and/or Mobile Equipment Identifier (MEID) screening toallow only designated MSs to access the femtocell. Configuration of thefemtocell system 350 with ESN(s) or MEID(s) may be made as part of aninitial femtocell system 350 activation.

In another embodiment, a femtocell system 350 may be implemented as a3G-complinat entity, e.g., to service UMTS mobile terminals, and may bedeployed in a small office/home office (SOHO) or other suitableenterprise. To this end, the femtocell system 350 may include anintegrated RNC and radio node (RN). In a particular implementation, thefemtocell system 350 may be implemented as an Evolution-Data Optimized(EV-DO) entity, e.g., a 1xEV-DO integrated IP-RAN. The femtocell system350 provides an IP-accessible radio access network and provides radiolink control functions.

FIG. 3B is a diagrammatic representation of an alternative networksystem 301 in which a femtocell system implemented in accordance with anembodiment of the invention may be deployed. System 301 includes amobile core network 310 implemented as, for example, a CDMA core networkthat interfaces with a SS7 network 370. The mobile core network 310 mayinclude an MC 312, an HLR 314, an AC 315, an MSC 316, and a PDSN 318,and various other components as described above with regard to themobile core network 310 of FIG. 3A.

System 301 includes an IP Multimedia Subsystem (IMS) core network 321that interfaces with the SS7 network 370. In accordance with anembodiment, the IMS core network 321 includes a CS 322, a MGCF 325, anMGW 326, an X-Call Session Control Function (X-CSCF) 328, and a HomeSubscriber Server (HSS) 329 among other components. The X-CSCF 328processes SIP signaling packets and provides a centralized interface forcontrol and signaling including SIP registration functions in accordancewith disclosed embodiments. The X-CSCF 328 may provideInterrogating-CSCF (I-CSCF) services, Proxy-CSCF (P-CSCF) services, andServing-CSCF (S-CSCF) services. The X-CSCF 328 comprises various SIPservers or proxies that process SIP signaling packets in the IMS corenetwork 321. P-CSCF services provided by X-CSCF may include provisioninga first point of contact for an IMS-compliant MS. In such a situation,the X-CSCF may be located in a visited network or in an MS's homenetwork if the visited network is not fully IMS-compliant. An MS maydiscover the X-CSCF 328, e.g., by using Dynamic Host ConfigurationProtocol (DHCP), or by assignment in a packet data protocol context.S-CSCF services provided by the X-CSCF 328 include provisioning as acentral node of the signaling plane. To this end, the S-CSCF comprises aSIP server, but additionally performs session control. Further, theX-CSCF 328 is interfaced with the HSS 329 and/or HLR 314 to download andupload user profiles for providing S-CSCF services. The X-CSCF 328further includes a SIP function for providing I-CSCF services. To thisend, the X-CSCF 328 has an IP address that is published in the DomainName System (DNS) that facilitates location of the X-CSCF 328 by remoteservers. Thus, I-CSCF services of the X-CSCF 328 may be used as aforwarding point for receipt of SIP packets within the domain.

The CS 322 may be configured to operate as an IMS application serverthat interfaces with the X-CSCF 328 using the ISC interface. The HSS 329comprises a user database that supports IMS network entities that manageor service calls. The HSS 329 contains subscription-related information,e.g., subscriber profiles, may perform authentication and authorizationof users, and may provide information about locations of MSs and IPinformation. In a fully standard IMS architecture, the CS 322 mayinterface with the HSS 329. However, in other scenarios, the HLR 314 mayanchor the service even with the HSS 329 deployed within the system 301.Accordingly, the CS 322 may be communicatively interfaced with the HLR314 for location updates using, for example, a TIA-41 interface.Further, the CS 322 is preferably interfaced with the MC 312 using, forexample, a TIA-41 interface.

The CS 322 may be communicatively coupled with the SS7 network 370, theMGCF 325, e.g., via SIP communications, the X-CSCF 328, e.g., via ISC,and the HSS 329, e.g., via an Sh interface. The MGCF 325 may becommunicatively coupled with the MGW 326, e.g., via an Mn interface, theX-CSCF 328, e.g., via an Mg interface, and the SS7 network 370 inaddition to the CS 322. The MGW 326 may be communicatively coupled withthe SS7 network 370 and a PDIF 332 in addition to the MGCF 325. The MGW326 may convert data between RTP and PCM, and may also be employed fortranscoding. Resources of the MGW 326 may be controlled by the MGCF 325.The X-CSCF 328 may be communicatively coupled with the PDIF 332 forexchanging SIP communications therewith and the HSS 329, e.g., via a Cxinterface, in addition to the CS 322 and the MGCF 325. The HSS 329 maybe communicatively coupled with the SS7 network 370, e.g., via IS-41,and a SS 330, e.g., via a Wx interface. The SS 330 may be coupled withthe PDIF 332, e.g., via a Wm interface.

The PDIF 332 facilitates access to the IMS core network 321 via WiFiaccess points and may be responsible for such services as, for example,security, access, authentication, policy enforcement, user informationcollection, and IP address allocation as well as other services. ThePDIF 332 may have RTP communications with the MGW 326. Further, the PDIF332 may have secured IP communications, e.g., IPsec, established withone or more femtocell systems, e.g., a femtocell system 350 deployed ata user premise, such as a home office. The secured communications may beestablished between the PDIF 332 and the femtocell system 350 over, forexample, a broadband network 360 interface such as residential DSL orcable broadband connection. The femtocell system 350, in turn, providesa radio access point for one or more MSs 325 when the MS 325 is withinrange of the femtocell system 350 with which the MS 325 has authorizedaccess.

FIG. 4 is a simplified diagrammatic representation of femtocell system350 that facilitates provisioning of a femto-RAN in accordance with anembodiment. Femtocell system 350 includes an antenna 410 coupled with aRN 412. RN 412 may be implemented, for example, as a 1xEV-DO ASIC devicefor provisioning a 1xEV-DO Rev. 0 air interface or a 1xEV-DO Rev. A airinterface. RN 412 may be communicatively coupled with a RNC 414 thatprovides radio control functions, such as receiving measurements fromMSs, control of handovers to and from other femtocell systems, and mayadditionally facilitate handoff to or from macrocells. RNC 414 may alsoprovide encryption/decryption functions, power, load, and admissioncontrol, packet scheduling, and various other services.

Femtocell system 350 includes an electronic serial number screeningfunction 416 that may facilitate approving or rejecting service for anMS by femtocell system 350. Additionally, femtocell system 350 includesan Internet Operating System (IOS) and SIP Adapter (collectivelyreferred to as IOS-SIP Adapter 418). IOS-SIP adapter 418 may invoke andmanage SIP clients, such as a user agent (UA) pool comprising one ormore UAs. Each MS authorized to be serviced by femtocell system 350 mayhave a UA allocated therefor by femtocell system 350 in a manner thatfacilitates transmission of communications to and from an MS over an IPbackhaul. Accordingly, when an authorized MS is within the femtocellsystem 350 site range, telecommunication services may be provided to theMS via the IP backhaul and the femtocell system 350 provisioned RAN.When the MS is moved beyond the service range of femtocell system 350,telecommunication service may then be provided to the MS viamacrocellular coverage. Femtocell system 350 may perform a DNS/ENUMregistration on behalf of MSs authorized to obtain service fromfemtocell system 350 and may generate and issue a SIP registration onbehalf of an MS authorized for service access by the femtocell system350.

FIG. 5 depicts a block diagram of a data processing system that may beimplemented as a convergence server 322 in accordance with an embodimentof the present invention. CS 322 may be a symmetric multiprocessor (SMP)system including a plurality of processors 502 and 504 connected to asystem bus 506. Alternatively, a single processor system may beemployed. Also connected to system bus 506 is memory controller/cache508 which provides an interface to local memory 509. An I/O bus bridge510 is connected to system bus 506 and provides an interface to an I/Obus 512. Memory controller/cache 508 and I/O bus bridge 510 may beintegrated as depicted.

Peripheral component interconnect (PCI) bus bridge 514 connected to I/Obus 512 provides an interface to PCI local bus 516. A number of modemsmay be connected to a PCI local bus 216. Communication links to clientsmay be provided through a modem 518 and network adapter 520 connected toPCI local bus 516 through add-in connectors.

Additional PCI bus bridges 522 and 524 provide interfaces for additionalPCI local buses 526 and 528, from which additional modems or networkadapters may be supported. In this manner, server 322 allows connectionsto multiple system nodes. A memory-mapped graphics adapter 530 and harddisk 532 may also be connected to I/O bus 512 as depicted, eitherdirectly or indirectly.

Those of ordinary skill in the art will appreciate that the hardwaredepicted in FIG. 5 may vary. For example, other peripheral devices, suchas optical disk drives and the like, also may be used in addition to orin place of the hardware depicted. The depicted example is not meant toimply architectural limitations with respect to the present invention.

While the CS 322 depicted in FIG. 5 comprises an SMP system, it shouldbe understood that any variety of server configurations andimplementations may be substituted therefor. The depicted server 322 isprovided only to facilitate an understanding of disclosed embodiments,and the configuration of the CS 322 is immaterial with regard to thedisclosed embodiments.

In many CDMA networks, a subscriber is uniquely identified by thecombination of an electronic serial number (ESN) and a mobileidentification number (MIN). A mobile equipment identifier (MEID) is anextension of the ESN that facilitates an increase in the number ofmanufacturers' codes. A pseudo-ESN (p-ESN) may be derived from the MEIDto be used in place of the ESN. The MIN-ESN, or MIN-p-ESN, combinationis used primarily for registration and authentication functions.Contemporary CDMA MSs may support an international mobile stationidentity (IMSI) and use the IMSI in place of the MIN to offer animproved address space and utilization by international applications.With the introduction of IMSI, the concept of a mobile station identitymay be either an MIN or an IMSI. Due to the variations in differentparameters for identification, it is assumed herein that a uniqueidentifier is included in the username portion of the To Header of aSIP:REGISTER request to create and identify the mobile stationsubscriber during the registration procedures described hereinbelow.This unique identifier is referred to herein as the register ID (RegID).An optional network dependent predefined prefix may be stripped from theregister ID prior to use in the convergence server functions. Theregister ID may contain an MIN or an IMSI paired with either an MEID, anESN, or a p-ESN. However, other options may be suitably implementedwithout departing from the disclosed embodiments.

In accordance with an embodiment, the CS 322 emulates the functionalityof a MSC and Visitor Location Register (VLR) to facilitateauthentication and registration of MSs in a carrier's CDMA network. Tothis end, the CS 322 may interface with the HLR 314 for authentication,location updates, and other services using an IS-41 interface.

In a pre-IMS environment, e.g., such as network system 300 depicted inFIG. 3A, the CS 322 receives a SIP:REGISTER message directly from thefemtocell system 350, or from the femtocell system 350 acting as a proxyfor the MS 325. The CS 322 provides SIP registration functions and isthe central interface point to the softswitch/MGCF 324 and VoIPelements.

In an IMS network such as network system 301 depicted in FIG. 3B, the CS322 functions as an IMS application server, and the IMS infrastructureprovides the centralized interface control and signaling including SIPregistration functions. In this environment, the femtocell system 350itself, or alternatively the femtocell system 350 acting as a proxy forthe MS 325, sends a SIP:REGISTER (e.g., via other CSCFs) to the S-CSCFwhich performs a third-party registration of the MS 325 with the CS 322based on initial filter criteria stored in the HSS 329.

In an embodiment, the femtocell system 350 may be configured to support“Global Challenge” based authentication on all system access (e.g.,Registration, Call Origination, Call Termination, and Data Burstmessages). The femtocell system may indicate a Global Challenge requestby setting an authentication bit (e.g., AUTH=1) in the overhead messagetrain (OMT). The femtocell system 350 may also include a global randomchallenge value (RAND) used in generating the authentication result byboth the MS and the HLR/AC.

The femtocell system preferably establishes an IPsec tunnel over thebroadband network with the PDIF 332 or, alternatively, a P-CSCF beforesending any SIP traffic to the CS 322. The IPsec tunnel may beestablished immediately after the femtocell system 350 is powered on orwhen an MS 325 attempts to establish a connection with the femtocellsystem 350. In this implementation, the CS 322 is not involved inestablishing the IPsec tunnel.

In an embodiment, the CS 322 may be configured to receive CDMA-1xauthentication data at the end of a SIP registration message using aSIP:MESSAGE received from the femtocell system 350. In this manner, theCS 322 conveys the result of the 1x authentication and, if needed,performs various authentication procedures, such as a unique challenge,SSD update, and a call history count.

FIG. 6 depicts a diagrammatic representation of a registration andauthentication process 600 on initial system access by an MS via afemtocell system in a non-IMS network, such as network system 300depicted in FIG. 3A, implemented in accordance with an embodiment. A SIPregistration phase is invoked by transmission of an OMT by the femtocellsystem 350 (step 602). An OMT facilitates autonomous registration andmay, for example, be transmitted on paging/access channels. Transmissionof the OMT by the femtocell system 350 may be made at a predefinedinterval, e.g., once a second. The OMT may include parameters for systemand region identification and may be distinguished from OMTs transmittedby other entities, e.g., by macro BTSs. An MS 325 in idle mode maydetect the OMT when the MS 325 is within range of the femtocell system350. In accordance with an embodiment, the OMT transmitted by thefemtocell system 350 includes an authentication bit (AUTH) having avalue, e.g., “1”, that indicates authentication is required for allsystem access. Further, the OMT includes a random number (RAND)generated by the femtocell system 350.

Based on the values in the OMT, the MS determines that a new servingsystem has been encountered and that authentication is required based onthe authentication bit value (AUTH=1). Subsequently, the MS 325 attemptsto obtain the random number (RAND) to be used for the authenticationfrom the OMT. If the random number is not available, a zero value may beused by the MS as prescribed by TR-45 authentication procedures. The MS325 then generates an authentication result (AUTHR). For example, the MS325 may generate an authentication result from a shared secret data key(SSD-A) stored by the MS 325, the ESN or p-ESN, the MIN, and the RANDvalue obtained from the OMT. The authentication result may be generated,for example, by execution of the well known CAVE algorithm by the MS325. The MS then transmits a registration request to the femtocellsystem 350 (step 604). The register message may include the MS's MIN,ESN or p-ESN, the authentication result (AUTHR), a CallHistoryCount(COUNT), and a random confirmation (RANDC) derived from the randomnumber (RAND) used to compute the authentication result (AUTHR).

On receiving the registration request from the MS 325, the femtocellsystem 350 sends a SIP:REGISTER message to the CS 322 (step 606) inaccordance with an embodiment that includes the unique register IDassociated with the MS, e.g., derived from an MIN or an IMSI paired witheither an MEID, an ESN, or a p-ESN.

Optionally, the femtocell system 350 may establish an IPsec tunnel withthe PDIF 332. The CS 322 then acknowledges receipt of the SIP:REGISTERmessage by transmitting a 200 OK SIP response to the femtocell system350 (step 608).

A registration phase is then invoked by the femtocell system 350transmitting 1x authentication parameters received from the MS 325 atstep 604 to CS 322 in a SIP: MESSAGE(LOCATION UPDATING REQUEST) (step610). The location updating request message includes the random number(RAND) rather than the random number confirmation (RANDC). The locationupdating request message additionally may include parameters, such as aRegister ID, ESN, MEID, MIN, IMSI, etc. Using the Register ID, the CS322 may associate the location updating request with the precedingSIP:REGISTER request received thereby from the femtocell system 350 instep 606. If the location updating request message includes aP-Access-Network-Info (PANI) header that may specify information aboutthe access technology, the CS 322 may save the PANI information.

The CS 322 acknowledges receipt of the location updating request messageby transmitting a 200 OK SIP response to the femtocell system 350 (step612). Network authentication and registration then occurs via exchangesbetween the CS 322 and HLR/AC (step 614). As part of the authenticationresponse, the HLR/AC may trigger Unique Challenge, SSD update, orCountUpdate procedures.

The CS 322 informs the femtocell system 350 of the authentication andregistration results by transmitting a SIP location updating responsemessage to the femtocell system 350 (step 616). In the event of anauthentication or registration failure, the CS 322 may send aSIP:MESSAGE containing, for example, an XML-encoded message body thatfacilitates deregistration of the femtocell system 350. The femtocellsystem 350 acknowledges receipt of the authentication and registrationresults by sending a 200 OK SIP response to the CS 322 (step 618). Inthe event of either a registration or authentication failure, aderegistration process 630 is invoked by the femtocell system 350transmitting a deregistration message, e.g., a SIP: REGISTER messagewith an expire value “0”, to the CS 322 (step 620). The CS 322acknowledges receipt of the deregistration message by transmitting a 200OK SIP response to the femtocell system 350 (step 622).

FIG. 7 depicts a diagrammatic representation of a registration andauthentication process 700 on initial system access by an MS via afemtocell system in an IMS network, such as network system 301 depictedin FIG. 3B, implemented in accordance with an embodiment. In thisimplementation, it is assumed that the MS comprises a standard 1x mobilephone and the femtocell system 350 is configured to operate as an IMSclient on behalf of the mobile stations attached with the femtocellsystem 350. When an MS attempts to establish a connection with thefemtocell system 350, the femtocell system 350 first attempts toregister in the IMS network on behalf of the MS. As part of theregistration, the IMS network may perform IMS-AKA authentication or,alternatively, allow the registration without performing anyauthentication. Further, in the described implementation, it is assumedthat the CS 322 is configured to act as an application server (AS) inthe IMS domain, and that it receives 3rd-party registration requestsfrom the S-CSCF at the end of the IMS network registration process.

The femtocell system 350 transmits an OMT (step 702) at a predefinedinterval. An MS 325 in idle mode may detect the OMT when the MS 325 iswithin range of the femtocell system 350 as described above withreference to FIG. 3A. The OMT transmitted by the femtocell system 350may include an authentication bit (AUTH) having a value, e.g., “1”, thatindicates authentication is required for all system access, and a randomnumber (RAND) generated by the femtocell system 350. On receipt of theOMT, the MS determines that a new serving system has been encounteredand that authentication is required based on the authentication bitvalue (AUTH=1). Subsequently, the MS 325 attempts to obtain the randomnumber (RAND) to be used for the authentication from the OMT. If therandom number is not available, a zero value may be used by the MS asprescribed by TR-45 authentication procedures. The MS 325 then generatesan authentication result (AUTHR), and transmits a registration requestto the femtocell system 350 (step 704). The registration message mayinclude the MS's MIN, ESN or p-ESN, the authentication result (AUTHR), aCallHistoryCount (COUNT), and a random number confirmation (RANDC)derived from the random number (RAND) used to compute the authenticationresult (AUTHR).

An IMS registration phase 730 is then initiated by the femtocell system350 sending a registration request to the S-CSCF (step 706). The S-CSCFthen sends a 3rd-party registration request to the CS 322 (step 708),and the CS 322 returns a 200 OK SIP response to the S-CSCF (step 710)for the 3rd-party registration which completes the IMS networkregistration.

If the registration fails, the CS 322 informs the femtocell system 350to perform IMS network deregistration. Assuming the registration issuccessful, an authentication process is then invoked by the femtocellsystem 350 transmitting 1x authentication parameters received from theMS 325 at step 704 to CS 322 in a SIP:MESSAGE(LOCATION_UPDATING_REQUEST) (step 712). The location updatingrequest message includes the random number (RAND) rather than the randomnumber confirmation (RANDC). The location updating request messageadditionally may include parameters, such as a Register ID, ESN, MEID,MIN, IMSI, etc. If the location updating request message includes aP-Access-Network-Info (PANI) header that may specify information aboutthe access technology, the CS 322 saves the PANI information.

The CS 322 acknowledges receipt of the location updating request messageby transmitting a 200 OK SIP response to the femtocell system 350 (step714). Network authentication and registration then occurs via exchangesbetween the CS 322 and HLR/AC (step 716). As part of the authenticationresponse, the HLR/AC may trigger Unique Challenge, SSD update, orCountUpdate procedures.

The CS 322 informs the femtocell system 350 of the authentication andregistration results by transmitting a SIP location updating responsemessage to the femtocell system 350 (step 718). In the event of anauthentication or registration failure, the CS 322 may send aSIP:MESSAGE containing, for example, an XML-encoded message body thatfacilitates deregistration of the femtocell system 350. The femtocellsystem 350 acknowledges receipt of the authentication and registrationresults by sending a 200 OK SIP response to the CS 322 (step 720).

In the event of either a registration or authentication failure, aderegistration process 740 is invoked by the femtocell system 350transmitting a deregistration message, e.g., a SIP: REGISTER messagewith a expire value “0”, to the S-CSCF (step 722). The S-CSCFacknowledges receipt of the deregistration message by transmitting a 200OK SIP response to the femtocell system 350 (step 724). The S-CSCF thentransmits the deregistration message to the CS 322 (step 726) whichacknowledges receipt of the deregistration message by transmitting a 200OK SIP response to the S-CSCF (step 728) thereby completingderegistration of the MS.

The CS 322 may receive a SIP:REGISTER message for a subscriber who isnot currently SIP registered, but for whom the CS 322 maintainssubscription data from the HLR. For example, the CS 322 may maintain theHLR subscription information for a configurable period after a SIPderegistration. In this scenario, a MS re-registration procedure may beinvoked. The re-registration may be consistent with that as describedabove with reference to FIG. 6 except the CS 322 is not required torequest the user profile from the HLR.

Periodic registration is optionally required in mobile networks. Ifperiodic registration is enabled, the HLR may return an “AuthorizationPeriod” in response to a Registration Notification (REGNOT). In thiscase, the CS 322 may send a SIP:MESSAGE (ORDERED_REGISTRATION_REQUEST)before the “Authorization Period” expires. On receiving this request,the femtocell system 350 may send the ordered registration request tothe MS 325 to send registration-related parameters.

Regardless of an “Authorization Period” timer, the SIP registrationperiod dictates the interval at which the SIP registration from thefemtocell system 350 needs to be refreshed. In such a case, thefemtocell system 350 needs to refresh the registration prior to theexpiration period while the MS 325 is attached to the femtocell system350. Such registration procedures are preferably processed locally atthe CS 322. The femtocell system 350 sends a SIP:REGISTER message to theCS 322, and the CS 322 returns a SIP 200 OK response to the femtocellsystem 350.

When deregistration occurs, e.g., either due to registration timeout ormobile-initiated/network deregistration, the CS 322 may typically notdelete HLR subscriber data which is eligible to be aged out, or removedby a REGCANC message. The CS 322 may send a mobile station inactive(MSINACT) message to the HLR with the optional DeregistrationTypeparameter omitted which indicates that subscriber data is still beingmaintained by the CS 322. Such a situation may occur, for example, dueto the MS 325 being powered off and it is desirable to have thesubscription data available when the MS is powered back on. However, thetime the MS was last registered is maintained with the subscriptiondata.

If the MS does not re-register for a configurable time (e.g., 24 hours),the subscriber data may be deleted and an MSINACT message is sent to theHLR with the DeregistrationType set to “administrative reason”indicating that the subscriber data has been purged from the CS 322.This may also occur as needed to free up space in the database therebydeleting the oldest data first based on when it was last accessed.

A mobile initiated de-registration process may be invoked when the CS322 receives a SIP:REGISTER from the femtocell system 350 with a timeoutof zero for a current registration. In an IMS network, the CS 322 mayreceive this message from the S-CSCF as a 3rd-party SIP:REGISTERmessage. For example, such a de-registration may occur when thefemtocell system 350 receives a power-down indication from the MS, thefemtocell system 350 detects MS inactivity, or the femtocell system 350detects a loss of radio contact.

Deregistration may additionally occur due to location updating. When theMS registers in a macrocell, the HLR preferably notifies the CS 322accordingly. If the SIP registration for the corresponding MS iscurrently active, the CS 322 may send a SIP:MESSAGE (Deregister) to thefemtocell system 350 requesting it to deregister. Registrationcancellation may additionally occur due to administrative reasons aswell. In such a case, the MS may be in a call or using some networkservice. If the cancellation indicates that service is to bediscontinued immediately, the CS 322 terminates any call in progress.

In accordance with disclosed embodiments, mechanisms that facilitateindirect routing of mobile-originated short messages service (SMS)messages for a mobile station attached with a femtocell system areprovided. As is understood, SMS supports the transmission and receptionof simple messages. SMS may support various types of services. Forexample, an SMS bearer service may comprise a basic transport mechanismto convey an SMS message (with a length up to 200 octets) as a packet ofdata between two points or short message entities (SMEs) on the network.SMS teleservices may provide flexible custom applications forcommunication between SMS users (i.e., SMEs). These services require twofunctional entities in addition to those used for basic mobiletelecommunications. The message center (MC), e.g., MC 312, provides astore-and-forward function for most mobile originated short messages andfor all mobile-terminated short messages. MS-based SMEs are associatedwith an MC, known as the home MC, in the MS's home system. In thedescribed embodiments, it is assumed that the mobile core network 310comprises the MS's 325 home carrier network, and thus the MC 312comprises the MS's 325 home MC. A short-message entity, e.g., a mobilestation, a personal digital assistant (PDA), or any other suitable dataprocessing system adapted to communicatively interface with thefemtocell system 350 and the mobile core network 310 depicted in FIG. 3and further adapted to process SMS messages, comprises a functionalentity capable of composing and decomposing a short message.

The home MC may be bypassed for a mobile-originated short message, andthe SMS may be sent directly to a destination SME by the serving MSC(i.e., by direct routing procedures). In this case, no originatingsupplementary services may be applied to the message. In this instance,the CS, operating as the VLR/MSC (i.e., the location register andswitching center of the serving system), will use only indirect routingin accordance with an embodiment. That is, for mobile-originated shortmessages, the serving system, (i.e., the CS), will forward the shortmessage to the home MC. From there, the short message is sent to thedestination MC.

In accordance with an embodiment, mobile-originated short messages maybe delivered via indirect routing. Depending on the existence of anassigned traffic channel (e.g., an active voice call) for the MS and/orthe size of the SMS being sent, the MS may elect to use the traffic orpaging channel for delivery of a short message. In both scenarios it isassumed that the MS is registered with the CS 322. If the MS selects thetraffic channel for delivery of the SMS message and if there is noexisting traffic channel, the MS may first attempt to establish atraffic channel using the same procedure used while attempting toinitiate a voice call as described below with regard to block 850 ofFIG. 8. If an active traffic channel is already established between theMS and the femtocell system 350, then the steps of block 850 are notexecuted. Once the traffic channel is established, the MS sends the SMSmessage to the femtocell system which, in turn, forwards the SMS messageto the CS 322 using a SIP:MESSAGE.

If the MS elects to send the SMS message over a paging channel, it sendsthe SMS message along with the 1x authentication data to the femtocellsystem 350. Similar to the traffic channel SMS delivery scenario, thefemtocell first performs the authentication during steps 824-832 of FIG.8 as described more fully hereinbelow. Once the authentication result isreceived from the CS 322, the femtocell system then forwards the SMSmessage to the CS 322 using a SIP:MESSAGE.

FIG. 8 depicts a diagrammatic representation of a signaling flow 800 ofa mobile-originated SMS delivery procedure utilizing indirect routing inaccordance with an embodiment. The MS is successfully registered in thenetwork system (step 802), e.g., via a SIP registration process. The MSthen determines that authentication is required on all system accesses,e.g., on receipt of an Overhead Message Train (OMT) that includes anauthentication value (e.g., AUTH=1) that indicates authentication isrequired (step 804). The random number (RAND) to be used forauthentication may also be obtained by the MS from the OMT. If it isnot, a zero value may be used by the MS as prescribed by TR-45authentication. The MS executes an instance of the CAVE algorithm usingthe dialed digits of the device to which the SMS message is to bedelivered, the RAND, the ESN/p-ESN, and the SSD currently stored toproduce an origination Authentication Result (AUTHR).

In the event the MS elects to send the SMS message via a traffic channel(block 850), the MS then sends an SMS origination message to thefemtocell system providing the dialed digits, its MIN, ESN/p-ESN, theAuthentication Result (AUTHR), the CallHistoryCount (COUNT), and theRANDC calculated from the RAND used to compute the Authentication Result(AUTHR) (step 806). The femtocell system, on receipt of the SMSorigination attempt from the MS, may verify the RANDC value supplied bythe MS and send a service request message required for authenticationusing a SIP: MESSAGE(CM SERVICE REQUEST) to the CS (step 808) thatincludes the called and calling party numbers. The service requestmessage may include the RANDC, authentication result (AUTHR), and COUNTvalues supplied by the MS. The CS 322 may acknowledge receipt of theservice request by returning a SIP 200 OK response (step 810). The CSthen engages the mobile core network 310, e.g., the HLR 314/AC 315, inan authentication process to authenticate the MS (step 812).

The CS then forwards the result of the authentication to the femtocellsystem using a SIP message including a global challenge response (GLOBALCHALLENGE RESPONSE) along with the encryption information received fromthe HLR/AC and a locally generated authentication token (step 814). Thefemtocell system presents the authentication token received in theglobal challenge response to the CS in a subsequentSIP:MESSAGE(SMD-REQ). The CS may deny the SMS request if this token isnot received. If an active traffic channel is available due to an activevoice call just before sending the SMS message, the femtocell system 350has to include the authentication token provided while establishing thecall. The femtocell system acknowledges the receipt of the globalchallenge response message (step 816). Once the traffic channel isestablished between the MS and the femtocell system 350 (step 818), theMS sends the SMS message (SMD-REQ) to the femtocell system 350 (step820).

In the event the SMS message is to be delivered on the paging channel(block 852), the MS sends the SMS message (SMD-REQ) to the femtocellsystem along with the 1x authentication information (step 822). Thefemtocell system maintains the SMS message locally while performing the1x authentication procedures. To this end, the femtocell system, onreceipt of the SMS origination attempt from the MS, may verify the RANDCvalue supplied by the MS and send a service request message required forauthentication using a SIP: MESSAGE CM_SERVICE_REQUEST) to the CS (step824) that includes the called and calling party numbers. The servicerequest message may include the RANDC, authentication result (AUTHR),and COUNT values supplied by the MS. The CS 322 may acknowledge receiptof the service request by returning a SIP 200 OK response (step 826).The CS then engages the mobile core network 310, e.g., the HLR 314/AC315, in an authentication process to authenticate the MS (step 828). TheCS 322 forwards the result of the authentication to the femtocell systemusing a SIP message including a global challenge response (GLOBALCHALLENGE RESPONSE) along with the encryption information received fromthe HLR/AC and a locally generated authentication token (step 830). Thefemtocell system presents the authentication token received in theglobal challenge response to the CS in a subsequentSIP:MESSAGE(SMD-REQ). The CS may deny the SMS request if this token isnot received. The femtocell system acknowledges the receipt of theglobal challenge response message (step 832).

The SMS message is then delivered to the CS 322 (step 834). To this end,the femtocell system formats a SIP:MESSAGE with the content-type headerset to multipart/mixed and with binary SMD-REQ data in one message body(e.g., content-type=application/vnd.3gpp2.sms) and the authenticationtoken (AUTH_TOKEN) in a separate message body (e.g.,content-type=application/vnd.3gpp2.bsap+xml). If the validation of theauthentication token is successful, the CS 322 responds with a SIP “202Accepted” message, otherwise it returns a SIP “403 forbidden” message tothe femtocell system 350 (step 836).

The SMS message is then delivered to the MC 312 if the validation of theauthentication token is successful (step 838). The CS 322 creates a SIP:MESSAGE with the SMD-ACK for positive acknowledgement of the SMStransmission or, alternatively, SMD-NAK for negative acknowledgement ofthe short message delivery and sends it to the femtocell system 350(step 840). The femtocell system acknowledges receipt of the SMD-ACK orSMD-NAK by returning a SIP 200 OK response to the CS 322 (step 842) andforwards the SMD-ACK or SMD-NAK to the mobile station (step 844).

FIG. 9A is a diagrammatic representation of a service request message900 transmitted to the CS from the femtocell system implemented inaccordance with an embodiment. The service request message 900transmitted to the CS, e.g., according to step 808 or 824 of FIG. 8, maybe generated by the femtocell system in response to receipt of theorigination request received from the MS according to step 806 of FIG. 8or receipt of the SMS origination request received from the MS accordingto step 822 of FIG. 8. The service request message 900 may beimplemented as a SIP message including the depicted XML-encoded servicerequest message.

The service request message 900 is transmitted from the femtocell system350 to the CS 322 to authenticate an MS for a mobile-originated shortmessage. In an embodiment, the service request message 900 may include amessage body 920 that includes a service request message ID field 902 inwhich the femtocell system 350 provides a message identifier, e.g., a 32bit message identifier, to facilitate correlation between the requestand response(s). When a global challenge results in a unique challenge,SSD update, and/or count update, the CS 322 may include the same messageID in those transactions. The femtocell system 350 may initiate amaximum timer for response to the service request that is initiatedafter receiving the 200 OK response from the CS for the service request,e.g., according to step 810 or 826 of FIG. 8. The timer is stopped whenthe global challenge response is received by the femtocell system, e.g.,according to step 814 or 830 of FIG. 8. If the service request resultsin an SSD Update, Unique Challenge, and/or count update, the timeout maybe increased accordingly. The service request message 900 mayadditionally include a random number field 904 that includes the randomnumber (RAND) provided to the MS, e.g., according to step 804, used forauthentication, an authentication response field 906 that includes theauthentication response (AUTHR) generated by the MS, and a count field908. Further, the service request message body 920 may include thecalling party number digits 910. Alternatively, a service requestmessage body 922 may include authentication data 912 in lieu of thecalling party number digits.

FIG. 9B is a diagrammatic representation of a global challenge responsemessage 940 transmitted to the femtocell system 350 from the CS 322 inaccordance with an embodiment. The global challenge response message 940transmitted to the femtocell system, e.g., according to step 814 or step830 of FIG. 8, may be generated by the CS in response to theauthentication procedure performed between the CS and the HLR/ACaccording to step 812 or 828 of FIG. 8. The global challenge responsemessage 940 may be implemented as a SIP message including the depictedXML-encoded global challenge response message.

The global challenge response message 940 is transmitted from the CS 322to the femtocell system 350 in response to a service request and pagingauthentication request to convey the global challenge authenticationresult, authentication token, and the encryption information(CDMAPrivateLongCodeMask (CDMAPLCM), SignalingMessage EncryptionKey(SMEKEY), and VoicePrivacyMask (VPMASK) received from the AC. To thisend, the global challenge response message 940 may include a globalchallenge response message ID field 942, a successful authenticationfield 944 that includes an identifier, e.g., a Boolean value, thatspecifies whether the authentication was successful, and anauthentication token field 946 that includes the authentication token.Further, the global challenge response message 940 may include aCDMAPLCM field 948 that includes the CDMA private long code mask, aSMEKEY field 950 that includes the signaling message encryption key, anda VPMASK field 952 that includes the voice privacy mask in the event ofa successful authentication.

As described, mechanisms that facilitate indirect routing ofmobile-originated short messages for a mobile station attached with afemtocell system are provided. A convergence server operating as theVisitor Location Register/Mobile Switching Center uses indirect routingfor message delivery, e.g., by forwarding a mobile-originated shortmessage to the home message center of the mobile station. Thereafter,the short message is sent to the destination message center. Dependingon the existence of an assigned traffic channel for the MS and/or thesize of the SMS being sent, the MS may elect to use a traffic or pagingchannel for delivery of a short message. If the MS selects the trafficchannel for delivery of the SMS message and if there is no existingtraffic channel, the MS may first attempt to establish a trafficchannel. If an active traffic channel is already established between theMS and the femtocell system, the MS sends the SMS message to thefemtocell system which, in turn, forwards the SMS message to the CS. Ifthe MS elects to send the SMS message over a paging channel, the MSsends the SMS message along with 1x authentication data to the femtocellsystem. The femtocell system first performs the authentication, andsubsequently forwards the SMS message to the CS which, in turn, forwardsthe short message to the home message center of the MS that originatedthe SMS message.

The illustrative block diagrams depict process steps or blocks that mayrepresent modules, segments, or portions of code that include one ormore executable instructions for implementing specific logical functionsor steps in the process. Although the particular examples illustratespecific process steps or procedures, many alternative implementationsare possible and may be made by simple design choice. Some process stepsmay be executed in different order from the specific description hereinbased on, for example, considerations of function, purpose, conformanceto standard, legacy structure, user interface design, and the like.

Aspects of the present invention may be implemented in software,hardware, firmware, or a combination thereof. The various elements ofthe system, either individually or in combination, may be implemented asa computer program product tangibly embodied in a machine-readablestorage device for execution by a processing unit. Various steps ofembodiments of the invention may be performed by a computer processorexecuting a program tangibly embodied on a computer-readable medium toperform functions by operating on input and generating output. Thecomputer-readable medium may be, for example, a memory, a transportablemedium such as a compact disk, a floppy disk, or a diskette, such that acomputer program embodying the aspects of the present invention can beloaded onto a computer. The computer program is not limited to anyparticular embodiment, and may, for example, be implemented in anoperating system, application program, foreground or background process,driver, network stack, or any combination thereof, executing on a singleprocessor or multiple processors. Additionally, various steps ofembodiments of the invention may provide one or more data structuresgenerated, produced, received, or otherwise implemented on acomputer-readable medium, such as a memory.

Although embodiments of the present invention have been illustrated inthe accompanied drawings and described in the foregoing description, itwill be understood that the invention is not limited to the embodimentsdisclosed, but is capable of numerous rearrangements, modifications, andsubstitutions without departing from the spirit of the invention as setforth and defined by the following claims. For example, the capabilitiesof the invention can be performed fully and/or partially by one or moreof the blocks, modules, processors or memories. Also, these capabilitiesmay be performed in the current manner or in a distributed manner andon, or via, any device able to provide and/or receive information.Further, although depicted in a particular manner, various modules orblocks may be repositioned without departing from the scope of thecurrent invention. Still further, although depicted in a particularmanner, a greater or lesser number of modules and connections can beutilized with the present invention in order to accomplish the presentinvention, to provide additional known features to the presentinvention, and/or to make the present invention more efficient. Also,the information sent between various modules can be sent between themodules via at least one of a data network, the Internet, an InternetProtocol network, a wireless source, and a wired source and viaplurality of protocols.

What is claimed is:
 1. A method, comprising: receiving, by a convergenceserver deployed in a core network, a service request message for amobile station communicably coupled with a femtocell system, the servicerequest message having originated from the femtocell system after thefemtocell system receives a message from the mobile station, identifyinga destination mobile device to which the message will be sent;authenticating, by the core network, the mobile station; responsive tothe authentication process, transmitting, by the convergence server, aglobal challenge response to the femtocell system, the global challengeresponse message including an authentication token generated by theconvergence server; receiving, by the convergence server, a shortmessage originated by the mobile station from the femtocell system, theshort message identifying the device; determining, by the convergenceserver, whether the authentication token has been presented to theconvergence server by the femtocell system and denying the servicerequest message if the authentication token has not been presented tothe convergence server by the femtocell system; and if theauthentication token has been presented to the convergence server by thefemtocell system, transmitting, by the convergence server, the shortmessage to a home message center of the mobile station which thereaftertransmits the short message from the home message center of the mobilestation to a destination mobile center of the destination mobile device.2. The method of claim 1, wherein the short message is transmitted tothe femtocell system from the mobile station via a traffic channel andthe service request message is generated by the femtocell systemresponsive to receipt of an origination request from the mobile station,the method further comprising establishing a traffic channel between themobile station and the femtocell system.
 3. The method of claim 2,wherein the short message is received by the convergence serverresponsive to establishment of the traffic channel.
 4. The method ofclaim 1, wherein the service request message is generated by thefemtocell system responsive to receipt of a short message servicerequest including the short message from the mobile station.
 5. Themethod of claim 1, wherein the short message service request is receivedby the femtocell system on a paging channel.
 6. The method of claim 1,wherein the short message is received by the convergence server with theauthentication token.
 7. The method of claim 6, further comprisingvalidating, by the convergence server, the authentication token receivedwith the short message.
 8. The method of claim 7, wherein theconvergence server transmits the short message to the message centerresponsive to validating the authentication token received with theshort message.
 9. A non-transitory computer-readable medium havingcomputer-executable instructions tangibly embodied thereon for executionby a processing system that, when executed, cause the processing systemto: receive, by a convergence server deployed in a core network, aservice request message for a mobile station communicably coupled with afemtocell system, the service request message having originated from thefemtocell system after the femtocell system receives a message from themobile station, identifying a destination mobile device to which themessage will be sent; authenticate, by the core network, the mobilestation; transmit, by the convergence server, a global challengeresponse message including an authentication token to the femtocellsystem; responsive to the authentication process, transmit, by theconvergence server, a global challenge response to the femtocell system,the global challenge response message including an authentication tokengenerated by the convergence server; receive, by the convergence server,a short message originated by the mobile station from the femtocellsystem, the short message identifying the device; determine, by theconvergence server, whether the authentication token has been presentedto the convergence server by the femtocell system and denying theservice request message if the authentication token has not beenpresented to the convergence server by the femtocell system; and if theauthentication token has been presented to the convergence server by thefemtocell system, transmit, by the convergence server, the short messageto a home message center of the mobile station which thereaftertransmits the short message from the home message center of the mobilestation to a destination mobile center of the destination mobile device.10. The non-transitory computer-readable medium of claim 9, wherein theshort message is transmitted to the femtocell system from the mobilestation via a traffic channel and the service request message isgenerated by the femtocell system responsive to receipt of anorigination request from the mobile station, the computer-readablemedium further comprising instructions that, when executed by theprocessing system, cause the processing system to establish a trafficchannel between the mobile station and the femtocell system.
 11. Thenon-transitory computer-readable medium of claim 10, wherein the shortmessage is received by the convergence server responsive toestablishment of the traffic channel.
 12. The non-transitorycomputer-readable medium of claim 9, wherein the service request messageis generated by the femtocell system responsive to receipt of a shortmessage service request including the short message from the mobilestation and wherein the short message service request is received by thefemtocell system on a paging channel.
 13. The non-transitorycomputer-readable medium of claim 9, wherein the short message isreceived by the convergence server with the authentication token. 14.The non-transitory computer-readable medium of claim 13, furthercomprising instructions that, when executed by the processing system,cause the processing system to validate, by the convergence server, theauthentication token received with the short message.
 15. Thenon-transitory computer-readable medium of claim 14, wherein theconvergence server transmits the short message to the message centerresponsive to validating the authentication token received with theshort message.
 16. A system, comprising: a core network that includes aconvergence server; a mobile core network that includes anauthentication center, a Home Location Register, and a home messagecenter of the mobile station; and an Internet Protocol-based femtocellsystem that provides a radio access point for a mobile station, whereinthe convergence server receives a service request message for the mobilestation, the service request message having originated from thefemtocell system after the femtocell system receives a message from themobile station identifying a destination mobile device to which themessage will be sent, authenticates the mobile station in response toreceiving the service request, transmits a global challenge responsemessage including an authentication token to the femtocell system,responsive to the authentication process, transmits a global challengeresponse to the femtocell system, the global challenge response messageincluding an authentication token generated by the convergence server,receives a short message originated by the mobile station from thefemtocell system, the short message identifying the device, determineswhether the authentication token has been presented to the convergenceserver by the femtocell system and denies the service request message ifthe authentication token has not been presented to the convergenceserver by the femtocell system, and if the authentication token has beenpresented to the convergence server by the femtocell system, transmitsthe short message to the home message center which thereafter transmitsthe short message from the home message center of the mobile station toa destination mobile center of the destination mobile device.
 17. Thesystem of claim 16, wherein the short message is transmitted to thefemtocell system from the mobile station via a traffic channel and theservice request message is generated by the femtocell system responsiveto receipt of an origination request from the mobile station, andwherein a traffic channel is established between the mobile station andthe femtocell system and the short message is received by theconvergence server responsive to establishment of the traffic channel.18. The system of claim 16, wherein the service request message isgenerated by the femtocell system responsive to receipt of a shortmessage service request including the short message from the mobilestation, and wherein the short message service request is received bythe femtocell system on a paging channel.
 19. The system of claim 16,wherein the short message is received by the convergence server with theauthentication token, and wherein the convergence server validates theauthentication token received with the short message.
 20. The system ofclaim 19, wherein the convergence server transmits the short message tothe message center responsive to validating the authentication tokenreceived with the short message.